• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    methods and equipment to improve mechanisms for updating nfc data exchange configuration parameters. the aspects revealed here concern the improvement of mechanisms to prompt an nfcc to update data exchange parameters for iso-dep communications between a dh and a remote nfc endpoint. in an example, with an nfc device a dh can be configured to receive an activation message from an nfcc that is using an rf interface with frame through rf nfc-b technology, determine that one or more data exchange parameters are included in the activation message are different from one or more corresponding current relevant data exchange parameters that nfcc is configured to implement, generate an rf parameter update command that includes the data exchange parameter or parameters that correspond(s) to the parameter or current relevant data exchange parameters which are determined to be different and send the generated parameter update command to nfcc so as to prompt nfcc to update the corresponding current relevant data exchange parameter or parameters.
    公开号:BR112014007075B1
    申请号:R112014007075-0
    申请日:2012-09-28
    公开日:2021-06-29
    发明作者:John Hillan；Dubai Chingalande
    申请人:Qualcomm Incorporated；
    IPC主号:
    专利说明:

    Priority Claim in accordance with 35 U.S.C. §119
    [0001] This patent application claims priority to Provisional Application No. 61/542,027, entitled "METHODS AND EQUIPMENT TO IMPROVE NFC DATA EXCHANGE PARAMETER UPDATE MECHANISMS", filed on September 30, 2011 and assigned to assignee hereof and expressly incorporated herein by reference. Description of Prior Art
    [0002] The aspects disclosed refer generally to communications between devices and, more specifically, to methods and systems for improving mechanisms to prompt a Near Field Communications (NFC) (NFCC) controller to update parameters data exchange for international standards organizations data exchange protocol (ISO-DEP) communications between a device host (DH) and a remote NFC endpoint.
    [0003] Advances in technology have resulted in smaller and more powerful personal computing devices. For example, there are currently a number of handheld personal computing devices, which include wireless computing devices such as handheld cordless phones, personal digital assistants (PDAs) and alert devices, which are each small, lightweight, and lightweight. be easily ported by users. More specifically, portable cordless phones, for example, also include cellular phones that communicate voice and data packets over wireless networks. Many such cell phones are manufactured with ever-increasing computing capabilities and, as such, are becoming the equivalent of small personal computers and handheld PDAs. In addition, such devices are enabling communications that use various frequencies and applicable coverage areas, such as cellular communications, wireless local area network (WLAN), NFC communications, etc.
    [0004] When an NFC is implemented, an NFC enabled device may initially detect an NFC indicator and/or target device. Then, communications between NFC devices can use an ISODEP. This draft NFC Forum Controller Interface specification does not cover all of the functionality required to use ISO-DEP.
    [0005] Currently, the NCI defines two RF Interfaces that a device can use when communicating using the RF Protocol ISO-DEP: ISO-DEP and Quadro. If the NFC Controller is relatively sophisticated, it is capable of processing the ISO-DEP protocol and the ISO-DEP RF Interface can be used, reducing the processing load on the Device Host. If the NFC Controller is less capable and/or has a known bug, the RF Interface with Quadro can be used. In such an implementation, the NFC Controller merely passes the protocol enable, data and protocol disable messages to the Device Host for processing. Currently, when activating ISO-DEP using the RF Interface with Frame through NFC-B RF Technology, there are parameters in the activation command and response (ATRIB command and ATRIB response) that are required by the NFC Controller, but, since the NFC Controller merely passes the data to DH, the specification does not provide a mechanism for the NFCC to learn these values.
    [0006] Thus, improved equipment and methods are desirable to provide improved mechanisms for updating data exchange parameters for ISO-DEP communications between a DH and a remote NFC endpoint using interfaces such as an RF interface with frame and a protocol RF ISO-DEP. Invention Summary
    [0007] The following is a summary of one or more aspects in order to obtain a basic understanding of such aspects. This summary is not an overview of all aspects contemplated and is not intended to identify key or essential elements of all aspects or to delineate the scope of any or all aspects. Its purpose is to present some concepts of one or more aspects as an introduction to the more detailed description presented below.
    [0008] Several aspects are described in connection with the improvement of mechanisms to prompt an NFCC to update data exchange parameters for ISO-DEP communications between a DH and a remote NFC endpoint. In one example, with an NFC device a DH can be configured to receive an activation message from an NFCC that is using an RF interface with Quadro via RF NFC-B technology, determine that one or more data exchange parameters are included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement, generate an RF parameter update command that includes the one or more data exchange parameters that match the one or more current relevant data exchange parameters that are determined to be different and send the generated parameter update command to the NFCC in order to prompt the NFCC to update the corresponding one or more current relevant data exchange parameters .
    [0009] According to related aspects, a method is presented that improves mechanisms to prompt an NFCC to update data exchange parameters for ISO-DEP communications between a DH and a remote NFC endpoint. The method may include receiving, by a DH, an activation message from an NFCC that is using an RF interface with Quadro via NFC-B RF technology. The method may also include determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement. In addition, the method may include generating an RF parameter update command which includes the one or more data exchange parameters that correspond to the current relevant one or more data exchange parameters that are determined to be different. Furthermore, the method may include sending the generated parameter update command to the NFCC so as to prompt the NFCC to update the corresponding one or more current relevant data exchange parameters with the one or more data exchange parameters. data included in the RF parameter update command.
    [0010] Another aspect refers to a communication equipment. Communication equipment may include a device for receiving an activation message from an NFCC that is utilizing an RF interface with Quadro via RF NFC-B technology. The communication equipment may also include a device for determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement. In addition, the communication equipment may include a device for generating an RF parameter update command that includes the one or more data exchange parameters that correspond(s) to the one or more current relevant data exchange parameters that are determined as being different. Furthermore, the communication equipment may include a device for sending the generated parameter update command to the NFCC so as to prompt the NFCC to update the one or more current relevant data exchange parameters corresponding with the one or more data exchange parameters included in the RF parameter update command.
    [0011] Another aspect refers to a communication equipment. The equipment may include a DH configured to receive an activation message from an NFCC that is using an RF interface with Quadro through RF NFC-B technology. DH can also be configured to determine that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement. In addition, the DH can be configured to generate an RF parameter update command that includes the one or more data exchange parameters that correspond to the one or more current relevant data exchange parameters that are determined to be different. . Furthermore, DH can be configured to send the generated parameter update command to the NFCC in order to prompt the NFCC to update the corresponding one or more current relevant data exchange parameters with the one or more parameters of data exchange included in the RF parameter update command.
    [0012] Another aspect relates to a computer program product, which may have a computer readable medium comprising a code to receive, by a DH, an activation message from an NFCC that is using an RF interface with Frame through RF NFC-B technology. The computer readable medium may also include code to determine that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement. In addition, the computer readable medium may include code to generate an RF parameter update command that includes the one or more data exchange parameters that correspond to the current relevant one or more data exchange parameters that are determined to be different. Furthermore, the computer readable medium may include a code to send the generated parameter update command to the NFCC so as to prompt the NFCC to update the corresponding one or more current relevant data exchange parameters with the one. or more data exchange parameters included in the RF parameter update command.
    [0013] For the achievement of the foregoing and related purposes, the aspect or aspects comprise features fully described below and specifically pointed out in the claims. The following description and accompanying drawings set out in detail certain illustrative features of the appearance or aspects. These resources, however, indicate only a few of the many ways in which the principles of various aspects can be used, and this description is intended to include all such aspects and their equivalents.
    [0014] The features disclosed will be described below in conjunction with the accompanying drawings, presented to show and not limit the features disclosed, in which the same designations denote the same elements, and in which: Figure 1 is a block diagram of a wireless communication system according to an aspect; Figure 2 is a schematic diagram of a wireless communication system according to an aspect; Figure 3 is a block diagram of an NFC environment according to an aspect; Figure 4 is a flowchart describing an example of updating parameters when an RF ISO-DEP protocol is used with a framed RF interface with NFC-B technology, according to one aspect; Figure 5 is a call flow diagram depicting a example of updating parameters when an RF ISO-DEP protocol is used in listen mode with a framed RF interface with NFC-B technology, according to one aspect; Figure 6 is a call flow diagram depicting a example of updating parameters when an ISO-DEP protocol is used in query mode with a framed RF interface with NFC-B technology, according to one aspect; Figure 7 is a functional block diagram of an exemplary architecture of a communication device, according to an aspect; eFigure 8 is a functional block diagram of an exemplary communication system for updating parameters when an ISO-DEP protocol is used with a framed RF interface with NFC-B technology, according to one aspect. Detailed Description of the Invention
    [0015] Several aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are presented in order to obtain a complete understanding of one or more aspects. It should be understood, however, that such aspect(s) can be put into practice without these specific details.
    [0016] As described herein, a device may recognize an NFC target and/or indicator device when within range of the coverage area of the device and/or NFC reader/writer. The device may then obtain enough information to allow communications to be established. One form of communication that can be established is an ISODEP communication link. Communication between devices can be enabled through various RF NFC technologies, such as, but not limited to, NFC-A-NFC-B, etc.
    [0017] Generally, when activating the ISO-DEP query side through NFC-B using the RF Interface with Frame, a DH can select values for various data exchange communication parameters (TRO Minimum, TRI Minimum, TR2 Minimum, Suppress SoS and Suppress EoS, for example). DH can use some or all of these values in an enable command that it sends to the NFC Remote Endpoint. Since some or all of these values may be required by the local NFC Controller, DH can then compress these values into one octet, as defined in Table 4 below, into an RF_PARAMETER_UPDATE_CMD, and send an RF_PARAMETER_UPDATE_CMD to the NFCC. The NFCC can then extract the relevant values and use them as appropriate for subsequent data exchange.
    [0018] In addition, when activating the ISO-DEP listening side through NFC-B using the RF Interface with Frame, an NFC Controller can pass an activation command it receives from a remote NFC endpoint to a host of device (DH). DH can interpret the activation command received and, assuming it is valid, can extract various values from the command (TRO Minimum, TRI Minimum, TR2 Minimum, Suppress SoS and Suppress EoS, for example), or it can select values for some or all these variables. DH can then compress these values into one octet, as defined in Table 4 below, into an RF_PARAMETER_UPDATE_CMD, and send an RF_PARAMETER_UPDATE_CMD to the NFCC. The NFCC can then extract the relevant values and use them as appropriate for subsequent data exchange.
    [0019] Figure 1 shows a wireless communication system 100, in accordance with several exemplary embodiments of the present invention. Input power 102 is supplied to a transmitter 104 to generate an radiated field 106 to provide energy transfer. A receiver 108 couples to radiated field 106 and generates an output power 110 for storage or consumption by a device (not shown) coupled to output power 110. Both transmitter 104 and receiver 108 are separated by a distance 112. in an exemplary embodiment, the transmitter 104 and receiver 108 are configured in accordance with a mutual resonance relationship and, when the resonant frequency of the receiver 108 and the resonant frequency of the transmitter 104 are very close, the transmission losses between the transmitter 104 and receiver 108 are minimal when receiver 108 is located in the "near field" of radiated field 106.
    [0020] The transmitter 104 also includes a transmit antenna 114 to provide a device for transmitting power. A receiver 108 includes a receiving antenna 1108 as a device for receiving power. Transmitting and receiving antennas are dimensioned according to the applications and devices associated with them. As stated, an effective energy transfer occurs by coupling a large part of the energy in the near field of the transmitting antenna to a receiving antenna, not by propagating most of the energy in an electromagnetic wave to the far field. When in this near field, a mode of coupling can be developed between the transmit antenna 114 and the receive antenna 118. The area around antennas 114 and 118 where this near field coupling can occur is referred to herein as the mode region. coupling.
    [0021] Figure 2 is a schematic diagram of an exemplary near-field wireless communication system. Transmitter 204 includes an oscillator 222, a power amplifier 224n, and a filter and match circuit 226. The oscillator is configured to generate a signal at the desired frequency, which can be adjusted in response to the trim signal 223. The oscillator signal can be amplified by power amplifier 224 with a degree of amplification responsive to control signal 225. Filter and match circuit 226 can be included to filter out harmonics or other unwanted frequencies and match the impedance of the transmitter 204 to that of the antenna of transmission 214.
    [0022] The receiver 208 may include a matching circuit 232 and a rectifier and switching circuit 234 to generate a DC power output for charging a battery 236, as shown in Figure 2, or connecting a device coupled to the receiver (not shown ). Matching circuit 232 can be included to match the impedance of receiver 208 with that of receiving antenna 218. Receiver 208 and transmitter 204 can communicate on a separate communication channel 219 (such as Bluetooth, Zigbee , cell phone, etc.).
    [0023] Referring to Figure 3, a block diagram of a communications network 300 according to an aspect is shown. Communication network 300 may include a communication device 310, which, through antenna 324, may be in communication with a remote NFC endpoint 330 using one or more NFC 326 technologies (such as, for example, NFC-A, NFC- B, NFC-F, etc.). In one aspect, the remote NFC endpoint 330 can be triggered to communicate using the NFC module 332 through various interfaces, such as the RF interface with frame 334 and the RF interface ISO-DEP 336. In another aspect, the device communication terminal 310 and remote NFC endpoint 220 can establish an ISO-DEP communication link using an RF ISO-DEP protocol. In yet another aspect, the communication device 310 can be actuated to be connected to an access network and/or a core network (a CDMA network, a GPRS network, a UMTS network and other types of telephone line communications network. wires and wireless).
    [0024] In one aspect, the communication device 310 may include an NFC controller 312, an NFC controller interface (NCI) 322, and a device host 340. In one aspect, the device host 340 may be driven to obtain, through the NXCI 322 and the NFC Controller 312, information from the remote NFC endpoint 330, through the NFC module 332 of the remote NFC endpoint 330.
    [0025] In one aspect, during ISO-DEP communications, the 312 NFC Controller can operate using an ISO-DEP 316 RF interface. When operating using the ISO-DEP 316 RF interface, the 312 NFC Controller can be triggered to change various parameters associated with data exchange between device host 340 and remote NFC endpoint 330 using data exchange change module 318.
    [0026] The 340 device host can include, among other modules, a parameter selection module 342 and a parameter update module 344. From an operational aspect, when using an RF interface with frame 314, the NFC Controller 312 can act as a relay and merely communicate messages between device host 340 of communication device 310 and remote NFC endpoint 330. In such an aspect, NFC controller 312 may not interpret the content of messages relayed between device host 340 of device communication interface 310 and remote NFC endpoint 330. When using RF interface with frame 314 and NFC-B technology, NFC Controller 312, which functioned as an inquiry device or as a listening device, cannot interpret the message (ATRIB command or ATRIB response) and cannot, therefore, update the data exchange parameters included within the activation messages. In such an aspect, device host 340 may extract data exchange parameters from activation messages, whether received from remote NFC endpoint 330 or created by DH 340. In one aspect, data exchange parameters may include any combination of Minimum protection time (TR0), Minimum synchronization time (TR1), Minimum_frame delay time (TR2), Sequence Start Suppression (SoS) and Sequence End Suppression (EoS). The 344 parameter update module can communicate some or all of the data exchange values obtained by the 342 parameter selection module to the 312 NFC Controller. In addition, the 344 parameter update module communications can prompt the NFC Controller 312 in order to change various data exchange configuration parameters. In other words, since NFC Controller 312 may not detect the contents of activation messages, device host 340 can communicate the necessary data exchange parameters using parameter update module 344. parameters 344 can use message exchange as defined in Tables 1, 2, 3 and 4.Table 1: Control Message for Parameter Update Request:



    [0027] References within Tables 2 and 3 (Table 89, Table 91, Table 92) are made in the context of the NFC Forum NCI specification. In addition, references within Table 4 (DIGITAL) are made in the context of the NFC Forum DIGITAL Specification. Table 4 is not present in the NCI Forum NFC specification. As used herein with reference to Tables 1-4, there may be situations in which the DH 340 may attempt to communicate updates of certain data exchange parameters to the NFC 312 Controller. During such situations, the DH 340 sends a parameter update command (RF_PARAMETER_UPDATE_CMD, for example) to the NFC Controller 312. Table 1 presents an exemplary parameter update command.
    [0028] Continuing with the operational aspect described above with reference to Tables 2-4, when the NFC 312 Controller receives the update command (RF_PARAMETER_UPDATE_CMD, for example), the NFC 312 Controller responds with an update response (RF_PARAMETER_UPDATE_RSP, for example). Table 2 presents an exemplary parameter update response. In Table 2, the “Condition” field indicates whether the configuration of these RF Communication parameters was successful or not. For example, a “Condition” of CONDITION_OK will indicate that all RF Communication parameters have been set within the NFC 312 Controller at values included in the parameter update command. By contrast, if the DH 340 tries to set a parameter that is not applicable for the NFC 312 Controller, the NFC 312 Controller responds with a parameter update message (RF_PARAMETER_UPDATE_RSP, for example) with the “Condition” field as “invalid ” (PARAM_INVALID_CONDITION, for example) and the response may include one or more invalid RF Communication parameter IDs. In one respect, in case some parameters are invalid, the remaining valid parameters are still used by the NFC 312 Controller. Once the NFC 312 Controller has communicated the parameter update response (RF_PARAMETER_UPDATE_RSP, for example), the Controller of NFC 312 uses the data exchange parameter value values successfully updated at the appropriate time. For an inquiry device, the updated data exchange parameter values can be used when received. For a listening device, the updated data exchange parameter values can be used once the next RF Frame has been sent (as defined in the present NCI specification).
    [0029] Referring to Table 3, the “NFC-B Data Exchange Configuration” parameter specifies a number of NFC-B related values to be used by the NFCC during subsequent data exchange. This parameter includes values for TR0 Minimum, TR1 Minimum, TR2 Minimum, SoS Suppression and EoS Suppression. The octet format is defined in Table 4. In operation, not all values within the “NFC-B Data Exchange Configuration” parameter may be relevant in a given operating mode. In this regard, the NFC Controller can only update values that are relevant for the given operating mode.
    [0030] Therefore, the communications network 300 provides an environment to allow the updating of data exchange parameters in a 312 NFC Controller for ISO-DEP communication between a DH 340 and a remote NFC 330 endpoint when the NFC 312 is utilizing a framed RF interface and NFC-B technology.
    [0031] Figures 4-6 show several methodologies according to various aspects of the presented object. Although, for the purposes of simplifying the explanation, the methodologies are shown and described as a series of acts, it should be understood that the claimed object is not limited by the order of acts, since some acts may occur in orders other than those shown here and described and/or concomitantly with other acts. For example, those skilled in the art will understand that a methodology can alternatively be represented as a series of interrelated states or events, such as in a state diagram. Furthermore, not all acts shown may be necessary to implement a methodology according to the claimed object. In addition, it should also be understood that the methodologies disclosed below and throughout this report may be stored in an industrial product to facilitate transport and transfer of such methodologies to computers. The term industrial product, as used herein, is intended to encompass a computer program accessible from any computer-readable device, carrier, or medium.
    [0032] Referring now to Figure 4, an exemplary flowchart is shown describing a process 400 for updating data exchange configuration parameters for ISO-DEP communications between a DH and a remote NFC endpoint.
    [0033] As an optional aspect, in block 402, a data exchange process can be enabled using an RF ISO-DEP protocol with an RF interface with frame. In one aspect, the NFC-B technology is used by the NFCC in receiving and/or sending data associated with the enabled process.
    [0034] In block 404, DH can exchange activation messages with a remote NFC endpoint. In one aspect, activation messages are an ATRIB command and an ATRIB response and include one or more parameters associated with the data exchange configuration. In block 406, the DH can compare the relevant data exchange parameters currently used by the NFCC with the data exchange parameters provided in the received enable command.
    [0035] If, in block 406, the DH determines that none of the relevant parameters is different, under an optional aspect, in block 408 the DH can initiate communications with the remote NFC endpoint using the ISO-DEP protocol enabled. By contrast, if, at block 406, DH determines that one or more of the relevant data exchange parameters are different, then, at block 410, DH generates and transmits a parameter update message to the NFCC in order to display prompt the NFCC to update the currently used data exchange parameters to those included in the update message. This update can be performed upon receipt of the update message, or it can be delayed to a time following the transmission of the next RF Frame. In one aspect, parameter update messages can be formatted using the fields described in Tables 14. Specifically, the update can be immediate for an inquiry device, and delayed for a listening device. As noted in Tables 1-4, a reference to an NFC-B data exchange configuration table can be included in the RF parameter update command.
    [0036] As an optional aspect, in block 412 oDH can receive an RF parameter update response (RF_PARAMETER_UPDATE_RSP, for example) that indicates successful receipt and/or implementation of the data exchange parameters included in the RF parameter update command. Once the NFCC has updated one or more parameters, the process can continue to option block 408 to allow DH to initiate communications as a remote NFC endpoint using the ISO-DEP protocol enabled.
    [0037] Referring now to Figure 5, a call flow diagram on the listening side is shown that describes a system for updating parameters for ISO-DEP communications between a DH and a remote NFC endpoint using an NFCC. As shown in Figure 5, an NFC environment 500 can include a device host 502, an NFCC 504, and a remote NFC endpoint 506. The device host 502 can be implemented in Lookup Mode or Listen Mode. As used herein, an inquiry device is one that sent the initial command to which the listening device responded with a response. Then both devices will “transmit” and “receive” in turn. In other words, the inquiry device plays the role of a reader/writer, and the listening device plays the role of a card emulator.
    [0038] In act 508, the DH 502 can initiate communications to use an RF interface with frame in ISO-DEP RF protocol communications. In act 510, detection request and response communications can be sent between the NFCC504 and the remote NFC endpoint 506. In one aspect, in case NFC-B technology is used, the detection request can be a SOL_DETECB and the response detection can be a RES_DETECB. In act 512, an activation command (ATRIB command, for example) is transmitted from remote NFC endpoint 506 to NFCC 504. Once communications have been established using an RF framed interface, the message can be received as an RF Frame message (ATRIB command). In act 514, the NFCC 504 can recognize the message as a valid activation command that indicates an ISO-DEP protocol. In act 516, NFCC 504 may determine that the RF interface used in ISO-DEP protocol communications is “Frame”. In response to receiving a communication from the remote NFC endpoint, in act 518 the NFCC 504 may transmit an RF interface activation notification message (NTF_INTF_RF_ACTIVATED, for example) to the DH 502. In one respect, the notification may indicate the protocol as ISO-DEP and the interface as “Framework”. Furthermore, in response to the detection that the ISO-DEP protocol is “Frame”, in act 520 the NFCC 504 transmits the activation command to the DH 502.
    [0039] In act 522, the DH 502 can parse the activation command and extract data exchange parameters that are applicable to the NFCC 504 and can generate an update message that includes the relevant extracted data exchange parameters. In one aspect, the data exchange parameters include some or all of TR0 Minimum, TR1 Minimum, TR2 Minimum, SoS Suppression and EoS Suppression. In act 524, the DH 502 can transmit the update message to the NFCC 504. In one aspect, the update message is an RF_PARAMETER_UPDATE_CMD and includes the relevant extracted data exchange parameters. In addition, determined data exchange parameters can be selected to align with one or more parameters communicated as part of an ISO-DEP protocol update process.
    [0040] In act 526, the NFCC 504 can store the received data exchange parameters and, in act 526, an RF parameter update response (RF_PARAMETER_UPDATE_RSP, for example) can be transmitted by the NFCC 504 to the DH 502. act 528, the DH 502 transmits a response to the activation command and, in block 530, the response is relayed to the remote NFC endpoint 506. In act 532, the NFCC 504 can update data exchange parameters and exchange parameters of updated NFC-B data can be used for subsequent exchanges of ISO-DEP blocks at the specified time.
    [0041] Therefore, the data exchange parameters associated with the NFCC 504 are updated according to the activation command received in act 512 and, in act 534, the NFCC 504 can receive from the remote NFC endpoint 506 an ISO-block DEP, which can be relayed to DH 502 in act 536. In act 538, the received ISO-DEP block can be processed using ISO-DEP listen-side protocols, and in act 540 an ISO-DEP block can be transmitted to NFCC 504 so as to be relayed to remote NFC endpoint 506 in act 552.
    [0042] Referring now to Figure 6, an exemplary query-side call flow diagram is shown that describes a system for updating parameters for ISO-DEP communication between a DH and a remote NFC endpoint using an NFCC. As shown in Figure 6, an NFC 600 environment can include a 602 device host, an NFCC 604, and a remote NFC 606 endpoint.
    [0043] In act 608, the DH 602 can initiate communications in order to use an RF interface with frame for ISO-DEP RF protocol communications. In act 610, detection request and response communications can be sent between the NFCC 604 and the remote NFC endpoint 606. In one aspect, in case NFC-B technology is used, the detection request can be a SOL_DETECB and the detection response can be a RES_DETECB. In act 612, the NFCC 604 can transmit an RF interface activation notification message (NTF_INTF_RF_ACTIVATED, for example) to the DH 602. In one aspect, the notification can indicate the protocol as ISO-DEP and the interface as “Frame” . While operating in inquiry mode, the DH 602 can generate an activation command (ATRIB command, for example) that can be transmitted to the NFCC 604 in act 616. Since the NFCC 604 is using the RF interface with Quadro, the NFCC 604 can act as a relay and communicate the activation command to the remote NFC endpoint 606. The remote NFC endpoint 606 can receive the activation command, generate an activation response, and transmit the activation response (ATRIB response, for example ) in act 618. In act 620, the NFCC 604 transmits the activation response to the DH 602.
    [0044] In act 622, the DH 602 can parse the activation response and extract data exchange parameters that are applicable to the NFCC 604 and can generate an update message that includes the relevant extracted data exchange parameters. In one aspect, the data exchange parameters include some or all of TR0 Minimum, TR1 Minimum, TR2 Minimum, SoS Suppression and EoS Suppression. In act 624, the DH 602 can transmit the update message to the NFCC 604. In one aspect, the update message is an RF_PARAMETER_UPDATE_CMD and includes the relevant extracted or selected data exchange parameters. Furthermore, determined data exchange parameters can be selected to align with one or more parameters communicated as part of an ISO-DEP RF protocol update process.
    [0045] In act 626, NFCC 604 updates the parameter values on the query side with the values included in the command for use during data exchange. In act 628, an RF parameter update response (RF_PARAMETER_UPDATE_RSP, for example) can be transmitted by the NFCC 604 to the DH 602, indicating that the values have been updated.
    [0046] Therefore, the data exchange parameters associated with the NFCC 604 are updated according to the activation response received in act 620 and, in act 630, the DH 602 can generate an ISO-DEP block as part of the ISO communication -DEP with remote NFC endpoint 606. In act 632, the data block is communicated to NFCC 604, which retransmits the data to remote NFC endpoint 606 in act 634. In act 636, remote NFC endpoint 606 responds with an ISO-DEP block transmission to the NFCC 604 and, in act 638, the response can be retransmitted to the DH 602.
    [0047] Still referring to Figure 3, but now also referring to Figure 7, an exemplary architecture of communication device 700 is shown. As shown in Figure 7, communication device 700 includes a receiver 702, which receives a signal of, for example, a receiving antenna (not shown), performs typical actions (such as filtering, amplifying, downconverting, etc.) on the received signal, and digitizing the conditioned signal in order to obtain samples. Receiver 702 may comprise a demodulator 704, which may demodulate received symbols and send them to processor 706 for channel estimation. Processor 706 may be a processor dedicated to analyzing information received by receiver 702 and/or generating information for transmission by transmitter 720, a processor that controls one or more components of communication device 700, and/or a processor that both analyzes the received information. by receiver 702, generates information for transmission by transmitter 620, while controlling one or more components of communication device 700. In addition, signals can be prepared for transmission by transmitter 720 through modulator 718, which can modulate signals processed by processor 706 .
    [0048] The communication device 700 may further comprise a memory 708, which is operationally coupled to the processor 706 and which can store the data to be transmitted, the data received, information related to available channels, TCP streams, data associated with the analyzed signal and/or resistance to interference, information relating to the assigned channel, power, rate or the like and any other information for estimating a channel and communicating over the channel.
    [0049] In addition, processor 706, receiver 702, transmitter 720, NFCC 730 and/or DH 760 may provide a means for receiving an activation message from an NFCC 730 that is using an RF interface with Quadro over the NFC-B RF technology, means for determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC 730 is configured to implement, means for generating a RF parameter update command that includes the one or more data exchange parameters that correspond to the current relevant one or more data exchange parameters that are determined to be different and means for sending the generated RF parameter update command to the NFCC 730 in order to prompt the NFCC 730 to update the corresponding one or more current relevant data exchange parameters.
    [0050] It is to be understood that the data storage (memory 708, for example) described herein may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. By way of example, and not limitation, nonvolatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable PROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as an external cache memory. By way of example, not limitation, RAM is obtainable in many forms, such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDR SDRAM), SDRAM Enhanced (ESDRAM), Link Sync DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 708 of the present systems and methods may comprise, but are not limited to, these and other suitable types of memory.
    [0051] In another aspect, the communication device 700 may include an NCI 750. In one aspect, the NCI 750 may be powered to allow communications between a DH 760 and an NFC 730 controller.
    [0052] The communication device 700 may include an NFC 730 controller. In one aspect, the NFC 730 Controller may be triggered to obtain, through the NCI 750, information from other devices, such as the remote NFC endpoint 330. During With ISODEP communication, the NFC 730 Controller can operate using either an RF interface with frame 314 or an ISO-DEP 734 interface. When operating using the ISO-DEP 734 interface, the NFC 730 Controller can be triggered to change various parameters associated with communications between device host 760 and remote NFC endpoint 330 using data exchange change module 736.
    [0053] The 760 device host may include, among other modules, a parameter selection module 762 and a parameter update module 764. From an operational aspect, when using an RF interface with frame 732, the NFC Controller 730 can actuate as a relay and merely communicate messages between the device host 760 and a remote NFC endpoint. In such an aspect, the NFC controller 730 may not interpret the content of messages relayed between the device host 760 and the remote NFC endpoint. uses the RF interface with frame 732 and NFC-B technology, the NFC 730 Controller cannot interpret activation messages (ATRIB command or ATRIB response, for example) and therefore cannot update the data exchange parameters included in the messages activation. In such an aspect, device host 760 can extract data exchange parameters from activation messages exchanged with the remote NFC endpoint. In one aspect, the data exchange parameters can include any combination of Minimum protection time (TR0), Minimum synchronization time (TR1), Minimum frame delay time (TR2), Sequence Start Suppression (SoS) and End-of-sequence (EoS) suppression. The 764 parameter update module can communicate the relevant data exchange parameters obtained by the 762 parameter selection module to the 730 NFC Controller. In addition, the 764 parameter update module communications can prompt to the 730 NFC controller. in order to change various data configuration parameters. In other words, since the 730 NFC Controller may not detect the contents of the enable command, the 760 device host may communicate the necessary data exchange parameters to the 730 NFC Controller using the 764 parameter update module. As noted above , the parameter update module 764 can use message exchange as defined in Tables 1, 2, 3, and 4. Again, as noted above, the parameter update module 764 can update, once it has received, the parameter update command, or can retain the values (stored in memory 708, for example) for updating after the next RF Frame has been sent (as noted in the current NCI specification, for example).
    [0054] In addition, communication device 700 may include a user interface 740. User interface 740 may include input mechanisms 742 for generating inputs on communication device 700, and output mechanisms 744 for generating information for consumption by the user of communication device 700. For example, input mechanisms 742 may include a mechanism such as a key or keyboard, a mouse, a touchscreen monitor, a microphone, etc. In addition, for example, output mechanisms 744 may include a monitor, an audio speaker, a haptic feedback mechanism, a Personal Area Network (PAN) transceiver, etc. In the aspects shown, output mechanism 744 may include an actionable monitor for presenting media content that is presented in an image or video format or an audio speaker for presenting media content that is presented in an audio format. .
    [0055] In Figure 8 is shown an equipment 800 that improves mechanisms to prompt an NFCC in order to update data exchange parameters for ISO-DEP communications between a DH and a remote NFC endpoint and that can reside at least partially within a DH. It is to be understood that equipment 800 is represented as including functional blocks, which may represent functions implemented by a processor, software or a combination thereof (firmware, for example).
    [0056] Thus, the equipment 800 includes a logical grouping 802 of electrical components that can act together. For example, logical grouping 802 may include a device for receiving an activation message from an NFCC that is utilizing an RF interface with Quadro via RF NFC-B technology (Block 804). In one aspect, for example, device 804 may include the DH 760 of communication device 700 and/or processor 706 of communication device 700. In one aspect, the activation message may be an ATRIB command or an ATRIB response. In another aspect, the receiving device 804 may also be configured to receive an RF parameter update response from the NFCC, indicating that the one or more data exchange parameters have been successfully updated. In such aspect, the RF parameter update response can be an RF_PARAMETER_UPDATE_RSP message.
    [0057] In addition, logical grouping 802 may include a device for determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement (Block 806). In one aspect, for example, the device for determining 806 may include the DH 760 of the communication device 700 and/or the processor 706 of the communication device 700. In one aspect, the one or more data exchange parameters may include TR0 Minimum, TR1 Minimum, TR2 Minimum, Suppress SoS, EoS, etc. In another aspect, the one or more data exchange parameters may be determined to align with one or more parameters communicated as part of an RF ISO-DEP protocol update process.
    [0058] As an optional aspect, grouping 802 may include a device for generating an RF parameter update command that includes the one or more data exchange parameters that correspond to the current relevant data exchange parameters or parameters that are determined to be different ones (Block 808). In one aspect, for example, the 808 generating device may include the DH 760 of the communication device 700 and/or the processor 706 of the communication device 700. In one aspect, the 808 generating device may be configured to include a reference to a table of NFC-B data exchange settings in the RF parameter update command that includes a bitmask indicating the one or more data exchange parameters.
    [0059] In another optional aspect, logic grouping 802 may include a device to send the generated RF parameter update command to the NFCC in order to prompt the NFCC to update the one or more current relevant data exchange parameters corresponding with the one or more data exchange parameters included in the RF parameter update command (Block 810). In one aspect, for example, the sending device 810 may include the DH 760 of the communication device 700 and/or the processor 706 of the communication device 700. activation can be an activation response, and the NFCC can update the one or more data exchange parameters before transmitting the RF parameter update update response to DH. listen, the activation message could be an activation command. In such aspect, the NFCC can store the one or more data exchange parameters before transmitting the RF parameter update response to the DH, and the device to send can also be configured to send a wake-up response to the NFCC, and the NFCC may update the one or more data exchange parameters after sending the activation response message to a remote NFC endpoint. In one respect, the RF parameter update response may include an RF_PARAMETER_UPDATE_RSP message.
    [0060] In addition, equipment 800 may include a memory 812 that holds instructions for performing functions associated with electrical components 804, 806, 808 and 810.
    [0061] Although shown to be external to memory 812, it is to be understood that one or more of the electrical components 804, 806, 808, and 810 may exist within memory 812. In one respect, for example, memory 812 may be identical or similar to memory 708 (Figure 7). In another aspect, memory 812 may be associated with the DH 760 and/or the NFCC 730.
    [0062] As used in this application, the terms "component", "module", "system" and the like are intended to refer to a computer-related entity, such as, but not limited to, hardware, firmware, a combination of hardware and running software, software or software. For example, a component can be, but is not limited to, a process that runs on a processor, a processor, an object, an executable, an execution flow, a program and/or a computer. By way of illustration, both an application that runs on a computing device and the computing device can be a component. One or more components can reside within a process and/or flow of execution, and a component can be located on one computer and/or distributed among two or more computers. Furthermore, these components can be run from a variety of computer readable media that have a variety of data structures stored on them. Components can communicate through local and/or remote processes, for example, according to a signal that has one or more data packets, such as data from one component that interacts with another component in a local system , a distributed system and/or through a network, such as the Internet, with other systems through the signal.
    [0063] Furthermore, several aspects are described here in connection with a terminal, which can be a wired terminal or a wireless terminal. A terminal may also be called a system, device, subscriber unit, subscriber station, mobile station, mobile, mobile device, remote station, mobile equipment (ME), remote terminal, access terminal, user terminal, terminal, device device, user agent, user device, or user equipment (UE). A wireless terminal can be a cell phone, a satellite phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop station (WLL), a personal digital assistant (PDA) , a wireless-capable handheld device, a computing device, or other processing devices connected to a wireless modem. Furthermore, several aspects are described here in connection with a base station. A base station may be used to communicate with a wireless terminal or terminals and may also be referred to as an access point, Node B or some other terminology.
    [0064] Furthermore, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless otherwise specified, or clear from the context, the phrase “X uses A or B” is intended to mean any of the natural inclusive permutations. That is, the phrase “X uses A or B” is satisfied by any of the following occurrences: X uses A; X uses B; or X uses both A and B; In addition, the article "a" used in this application and in the appended claims is to be interpreted generally to mean "one or more" unless otherwise specified or clear in the context to be referred to a singular form.
    [0065] The techniques described here can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems.
    [0066] The terms "system" and "network" are often used interchangeably. A CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Broadband CDMA (W-CDMA) and other variants of CDMA. In addition, cdma2000 covers IS-2000, IS-95 and ISO-856 standards. A TDMA system can implement a radio technology such as the Global System for Mobile Communications (GSM). An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Mobile Ultra Wide Band (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA, which uses OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization called the “3rd Generation Partnership Project” (3GPP). In addition, cdma2000 and UMB are described in documents from an organization called “3rd Generation Partnership Project 2” (3GPP2). In addition, such wireless communication systems can additionally include non-hierarchical ad-hoc network systems (mobile to mobile, for example) that often use unlicensed unpaired spectrum, wireless LAN 802.xx, BLUETOOTH, field communications (NFC-A, NFC-B, NFC-F, etc.) and any other short-range or long-range wireless communication techniques.
    [0067] Various aspects or features will be presented in terms of systems that may include various devices, components, modules and the like. It should be understood that the various systems may include additional devices, components, modules, etc., and/or may not include all of the devices, components, modules, etc. discussed in connection with the figures. A combination of these approaches can also be used.
    [0068] The various logics, logic blocks, modules and illustrative circuits described in connection with the aspects disclosed herein can be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit ( ASIC), an array of field-programmable gates (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but alternatively the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as, for example, a combination of DSP and microprocessor, a series of microprocessors, one or more microprocessors together with a DSP core, or any other such configuration. Furthermore, at least one processor may comprise one or more actionable modules to perform one or more of the steps and/or actions described above.
    [0069] Furthermore, the steps and/or method or algorithm actions described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of media. storage known in the art. An exemplary storage medium may be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium can be integral with the processor. Also, in some respects, the processor and storage medium can reside in an ASIC. In addition, the ASIC can reside on a user terminal. Alternatively, the processor and storage medium can reside as discrete components on a user terminal. In addition, in some respects, method or algorithm steps and/or actions may reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or a computer-readable medium, which may be incorporated to a computer program product.
    [0070] Under one or more aspects, the functions described can be implemented in hardware, software, firmware or any combination of them. If implemented in software, functions can be stored or transmitted as one or more instructions or codes on a computer-readable medium. Computer readable medium includes both a computer storage medium and a communication medium which include any medium that facilitates the transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable medium may comprise a RAM, a ROM, an EEPROM, a CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices or any other means that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer. In addition, any connection can be called a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared , radio and microwave, so coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disc (disk and disc), as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disc and Blu-ray disc, where discs (disks) reproduce magnetically, as discs (discs) usually reproduce data optically with lasers. Combinations of the above elements should also be included within the reach of computer readable media.
    [0071] Although the foregoing disclosure discusses illustrative aspects and/or aspects, it should be noted that several changes and modifications can be made to them without abandoning the scope of the aspects described and/or the aspects defined by the appended claims. Furthermore, although elements of the described aspects and/or aspects may be described or claimed in the singular, the plural is contemplated, unless the limitation to the singular is explicitly stated. Furthermore, all or a portion of any aspect and/or aspect may be used with all or a portion of any other aspect and/or aspect, unless otherwise stated.
    权利要求:
    Claims (12)
    [0001]
    1. Communication method comprising: receiving (518, 612), by a device host (DH), an activation message from a near field communications controller (NFCC) that is using a radio frequency (RF) interface with Frame over of NFC-B RF technology; the method characterized in that it further comprises: determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement; generate an RF parameter update command that includes the one or more data exchange parameters that correspond to the current relevant one or more data exchange parameters that are determined to be different; and sending (524, 624) the generated RF parameter update command to the NFCC to prompt the NFCC to update the corresponding current one or more data exchange parameters with the one or more data exchange parameters included in the parameter update command RF.
    [0002]
    2. Method according to claim 1, characterized in that the one or more data exchange parameters comprise at least one parameter among: Minimum protection time (TRO), Minimum synchronization time (TR1), Minimum frame delay (TR2), Sequence Start Suppression (SoS), or Sequence End Suppression (EoS).
    [0003]
    3. Method according to claim 1, characterized in that generating further comprises: including a reference to an NFC-B data exchange configuration table in the RF parameter update command which includes a bit mask indicating the one or more data exchange parameters.
    [0004]
    4. The method of claim 1, further comprising: receiving (526, 628) an NFCC RF parameter update response that indicates that the one or more data exchange parameters have been successfully updated.
    [0005]
    5. Method according to claim 4, characterized in that the NFCC is in a query mode, in which the activation message is an activation response and in which the NFCC updates (626) the one or more parameters data exchange before transmitting the RF parameter update response to the DH.
    [0006]
    6. Method according to claim 4, characterized in that the NFCC is in a listen mode, in which the activation message is an activation command, and in which the NFCC stores (526) the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH, wherein the method further comprises sending (528) an activation response to the NFCC, and wherein the NFCC updates (532) the one or more parameters data exchange after sending the wake-up response message to a remote NFC endpoint.
    [0007]
    7. Method according to claim 1, characterized in that the activation message comprises an ATTRIB command or an ATTRIB response.
    [0008]
    8. Method according to claim 1, characterized in that the RF parameter update command comprises a RF_PARAMETER_UPDATE_CMD message.
    [0009]
    9. Method according to claim 4, characterized in that the RF parameter update response comprises an RF_PARAMETER_UPDATE_RSP message.
    [0010]
    10. Method according to claim 1, characterized in that the one or more data exchange parameters are determined so as to align with one or more parameters communicated as part of an RF ISO protocol update process -DEP.
    [0011]
    11. Computer readable memory characterized in that it comprises instructions stored therein, the instructions being computer executable to perform the method as defined in any one of claims 1 to 10.
    [0012]
    12. Equipment for communications characterized in that it comprises: device for carrying out the method as defined in any one of claims 1 to 10.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112014007075B1|2021-06-29|METHODS AND EQUIPMENT TO IMPROVE MECHANISMS FOR UPDATING NFC DATA EXCHANGE CONFIGURATION PARAMETERS
    US8989658B2|2015-03-24|Methods and apparatuses for improving NFC parameter update mechanisms
    US9735834B2|2017-08-15|Methods and apparatus for improving NFC activation and data exchange reporting mechanisms
    ES2628192T3|2017-08-02|Procedures and devices to improve an NFCEE discovery process
    EP2912780A1|2015-09-02|Methods and apparatus for discovering tag talks first devices
    US9113373B2|2015-08-18|Methods and apparatus for improving peer communications using an active communication mode
    TW201347440A|2013-11-16|Methods and apparatus for improving resolution among devices with different size NFC identifiers
    同族专利:
    公开号 | 公开日
    CN103843008B|2017-05-03|
    CN103843008A|2014-06-04|
    CN106650531A|2017-05-10|
    JP6076521B2|2017-02-08|
    CN106650531B|2019-06-04|
    MY168140A|2018-10-11|
    WO2013049651A1|2013-04-04|
    BR112014007075A2|2017-03-28|
    KR101826913B1|2018-02-07|
    AU2012315637A1|2014-03-27|
    KR20140082767A|2014-07-02|
    US8838026B2|2014-09-16|
    RU2014117791A|2015-11-10|
    US20130102247A1|2013-04-25|
    EP2761532A1|2014-08-06|
    US9112541B2|2015-08-18|
    SG11201400263VA|2014-05-29|
    CA2850004C|2016-08-09|
    US20150044967A1|2015-02-12|
    EP3319008A1|2018-05-09|
    JP2014534669A|2014-12-18|
    HUE036575T2|2018-07-30|
    EP2761532B1|2018-01-24|
    KR101576912B1|2015-12-11|
    JP5890026B2|2016-03-22|
    JP2016119705A|2016-06-30|
    ZA201403122B|2020-03-25|
    KR20150144815A|2015-12-28|
    RU2596579C2|2016-09-10|
    AU2012315637B2|2016-03-31|
    IL231317D0|2014-04-30|
    CA2850004A1|2013-04-04|
    IL231317A|2017-08-31|
    EP3319008B1|2021-03-31|
    ES2663414T3|2018-04-12|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    FR2760280B1|1997-03-03|1999-05-21|Innovatron Ind Sa|METHOD FOR MANAGING COLLISIONS IN A CONTACTLESS DATA EXCHANGE SYSTEM|
    JP2004215225A|2002-12-17|2004-07-29|Sony Corp|Communication system, communication method, and data processing device|
    US7353995B2|2003-04-10|2008-04-08|Siemens Energy & Automation, Inc.|Method and system for automated setup of configuration parameters for a control processor|
    JP4432787B2|2005-01-31|2010-03-17|ソニー株式会社|COMMUNICATION DEVICE, COMMUNICATION METHOD, AND PROGRAM|
    DE102005038872A1|2005-08-17|2007-02-22|Siemens Ag|Data exchange device|
    US8698603B2|2005-11-15|2014-04-15|Cisco Technology, Inc.|Methods and systems for automatic device provisioning in an RFID network using IP multicast|
    US8045996B2|2006-07-31|2011-10-25|Qualcomm Incorporated|Determination of cell RF parameters based on measurements by user equipments|
    FR2904741B1|2006-08-04|2009-10-02|Inside Contactless Sa|METHOD FOR ROUTING INPUT APPLICATION DATA IN AN NFC CHIPSET BY IDENTIFYING THE APPLICATION|
    US8588830B2|2007-02-02|2013-11-19|Inovus Solar, Inc|Wireless autonomous solar-powered outdoor lighting and energy and information management network|
    US20090192912A1|2008-01-30|2009-07-30|Kent Griffin|Charge-for-service near field communication transactions|
    EP2106107B1|2008-03-27|2012-04-18|Motorola Mobility, Inc.|Method and apparatus for automatic near field communication application selection in an electronic device|
    US8135379B2|2008-04-18|2012-03-13|Telefoanktiebolaget L M Ericsson |Auto-control of radiation power in a portable telecommunication system|
    EP2112634A1|2008-04-22|2009-10-28|Nec Technologies Limited|Method for transferring provisioning information to a mobile unit|
    WO2010008251A2|2008-07-18|2010-01-21|Lg Electronics Inc.|Apparatus for controlling a power and method thereof|
    EP2305002A4|2008-07-20|2015-04-08|Samsung Electronics Co Ltd|Method and system for managing multiple applications in near field communication|
    JP2010130242A|2008-11-26|2010-06-10|Sony Corp|Communication device and method, computer program, and communication system|
    US8593255B2|2009-04-24|2013-11-26|Nokia Corporation|Method and apparatus for providing user interaction via transponders|
    US20100330904A1|2009-06-30|2010-12-30|Nokia Corporation|Method, apparatus, and computer program product for refreshing a configuration of a contactless frontend device|
    US8224246B2|2010-05-10|2012-07-17|Nokia Corporation|Device to device connection setup using near-field communication|
    US20120045989A1|2010-08-18|2012-02-23|Nokia Corporation|Device discovery in near-field communication|
    JP5633336B2|2010-11-29|2014-12-03|ソニー株式会社|COMMUNICATION DEVICE AND COMMUNICATION METHOD, COMMUNICATION CONTROL DEVICE, COMMUNICATION CONTROL METHOD, AND PROGRAM|
    US8811896B2|2011-01-07|2014-08-19|Texas Instruments Incorporated|Non-volatile memory for contactless systems|
    US8838026B2|2011-09-30|2014-09-16|Qualcomm Incorporated|Methods and apparatus for improving NFC data exchange configuration parameter update mechanisms|US8150552B2|2007-02-26|2012-04-03|Gecko Alliance Group Inc.|Method, device and system for use in configuring a bathing unit controller|
    US9390298B2|2010-11-17|2016-07-12|Blackberry Limited|Application routing configuration for NFC controller supporting multiple NFCEEs|
    US8971800B2|2011-05-31|2015-03-03|Qualcomm Incorporated|Methods and apparatus for improving NFC activation and data exchange reporting mechanisms|
    US8838026B2|2011-09-30|2014-09-16|Qualcomm Incorporated|Methods and apparatus for improving NFC data exchange configuration parameter update mechanisms|
    US8690412B2|2012-03-15|2014-04-08|Apple Inc.|Backlight structures and backlight assemblies for electronic device displays|
    US9113373B2|2012-04-10|2015-08-18|Qualcomm Incorporated|Methods and apparatus for improving peer communications using an active communication mode|
    US9281872B2|2012-10-15|2016-03-08|Nxp B.V.|Near-field communication authentication|
    WO2014113991A1|2013-01-28|2014-07-31|华为终端有限公司|Nfc configuration method, nfc data transmission method, controller and nfc controller|
    US9294150B2|2013-02-06|2016-03-22|Hcl Technologies Limited|Information relay mechanism using proximity communication|
    US10645651B2|2013-06-12|2020-05-05|Qualcomm Incorporated|Methods and apparatus for improving re-activation of a NFC-F based remote NFC device|
    US9641959B2|2014-05-23|2017-05-02|Gecko Alliance Group Inc.|Household for industrial device including programmable controller and method device and system for use in configuring same|
    US9445482B2|2014-05-23|2016-09-13|Gecko Alliance Group Inc.|Light bulb and method and system for use in configuring same|
    US20160174267A1|2014-12-15|2016-06-16|Qualcomm Incorporated|Proprietary packet exchange for enhanced nfc communication|
    KR102288610B1|2017-12-19|2021-08-10|삼성전자주식회사|Radio frequency setting system and mobile device|
    CN108181823A|2017-12-29|2018-06-19|大连东软信息学院|Mixed networking formula smart home electric-control system|
    CN109615038A|2018-11-30|2019-04-12|阿里巴巴集团控股有限公司|Information processing method and device|
    EP3739766A1|2019-05-17|2020-11-18|Nxp B.V.|Nfc repeater system|
    法律状态:
    2018-12-11| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2019-11-12| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2021-04-20| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2021-06-29| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 28/09/2012, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US201161542027P| true| 2011-09-30|2011-09-30|
    US61/542,027|2011-09-30|
    US13/626,528|US8838026B2|2011-09-30|2012-09-25|Methods and apparatus for improving NFC data exchange configuration parameter update mechanisms|
    US13/626,528|2012-09-25|
    PCT/US2012/058032|WO2013049651A1|2011-09-30|2012-09-28|Methods and apparatus for improving nfc data exchange configuration parameter update mechanisms|
    [返回顶部]